feat: implement wave-2 compliance elements (A-08/A-09/A-11/B-03/B-04/D-01)#39
Merged
Conversation
Register the six wave-2 illustrative compliance elements (A-08 EntityEligibility, A-09 EquityOwnerLookThrough, A-11 ClaimFreshness, B-03 TransferRestrictionMetadata, B-04 EngineSelection, D-01 HolderCount) in ElementRegistry via DeployStack. A-09 is deployed first and injected into A-08's constructor as its ILookThroughSource; D-01 is constructed with the existing IdentityUniqueness/AccreditedInvestor addresses and CapMode.TWELVE_G, then wired to the engine via setEngine (mirroring SurveillanceFlag). Recipe requiredElements are intentionally left untouched.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
docs/elementswalkthrough specs as illustrative mock elements: A-08 EntityEligibility, A-09 EquityOwnerLookThrough, A-11 ClaimFreshness, B-03 TransferRestrictionMetadata, B-04 EngineSelection, D-01 HolderCount (stateful).ReasonCodes.encode(0, ELEMENT_ID, n)with per-element code tables mapped to the docs' §6.2 failure codes) and ships with a dedicated unit test file covering every failure code and boundary (strict-vs-inclusive thresholds, fail-closed defaults, direction rules).ILookThroughSourceseam; D-01 consumes A-04/A-03 via injected views, snapshots AI-ness at entry, and re-validates caps at commit (revertsComplianceRejectedon gate-to-commit races).DeployStackregisters all six (reciperequiredElementsintentionally untouched — deferred, recorded in FEATURES/PROGRESS as CMP-003).Verification
forge fmt --check,forge build,forge test --offline: 399/399 (36 suites).tools/deploy-v3mocha step is a local env gap — vendored tool untouched by this diff.)Specs:
docs/compliance/elements/on thedocs/elementsbranch.